Skip to main content

This is a new service – your feedback will help us to improve it.

Bristol City Council

Tree preservation zone

There is a problem

  • 368 entries with tree-preservation-order field must match the reference field in the tree preservation order dataset

21 Stoke Hill Bristol BS9 1JN

reference
7RTLH00ZX0297
name
21 Stoke Hill Bristol BS9 1JN
tree-preservation-order

undefined

402
tree-preservation-zone-type
group
geometry
MULTIPOLYGON (((-2.631854 51.475638,-2.631857 51.475641,-2.631885 51.475652,-2.631893 51.475657,-2.631902 51.475659,-2.631912 51.475668,-2.631915 51.475669,-2.631919 51.475670,-2.631933 51.475666,-2.631932 51.475668,-2.631934 51.475671,-2.631946 51.475675,-2.631975 51.475676,-2.631976 51.475680,-2.631981 51.475686,-2.631991 51.475689,-2.631995 51.475692,-2.632002 51.475702,-2.632011 51.475708,-2.632034 51.475717,-2.632041 51.475718,-2.632051 51.475728,-2.632064 51.475729,-2.632076 51.475736,-2.632082 51.475736,-2.632237 51.475630,-2.632051 51.475555,-2.631852 51.475472,-2.631743 51.475424,-2.631600 51.475527,-2.631600 51.475532,-2.631608 51.475544,-2.631623 51.475552,-2.631642 51.475557,-2.631647 51.475560,-2.631656 51.475570,-2.631661 51.475572,-2.631670 51.475572,-2.631679 51.475578,-2.631689 51.475576,-2.631690 51.475578,-2.631698 51.475582,-2.631718 51.475584,-2.631733 51.475598,-2.631760 51.475610,-2.631786 51.475612,-2.631795 51.475617,-2.631808 51.475621,-2.631826 51.475622,-2.631837 51.475620,-2.631840 51.475621,-2.631845 51.475631,-2.631854 51.475638)))
point
POINT (-2.631911 51.47558)
notes
YEW - Taxus baccata,LIME - Tilia x europaea,HORSE CHESTNUT - Aesculus hippocastanum
entry-date
2004-03-26
start-date
2004-03-26
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The Tree preservation zone guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that covers this zone.

How to improve Bristol City Council’s data

  1. Fix the errors indicated
  2. Use the check service to make sure the data meets the standard
  3. Publish the updated data on the endpoint URL